Repository navigation
update Jabber.at.xml - #4792
update Jabber.at.xml#4792
Conversation
|
A wildcard for the subdomains would also work here, given that the thing is already HSTS preloaded in some browsers. |
|
Oh sure, we really need a test for that. |
|
For catching preloadables, you mean? And if so, what should it do? In this case, preloadability has not yet descended all the way through to ESR, so current consensus appears to be that it should be treated on the same footing as all other rulesets. What I could see being useful would be to have a setup similar to what we use on Wikipedia where general maintenance scripts take care of things that we like but probably don't want to check on every single change; I'm thinking stuff like killing completely preloaded target hosts (which I'm still not certain I'm personally in favor of), enforcing a particular ruleset style, running https-everywhere-checker, etc. |
|
The test should check if a host sends the HSTS preload attribute and if the hosts is in the list. So we both agree that we don't want to maintain HSTS rulesets. A script could generate rules automatically during the build process out of the list (so they don't need to be in the repo). |
|
But how would we check if a host is in all of the relevant lists (without running in to the same problem as SSL Labs)? |
|
I think the list of Chrome and Firefox (if there are any differences) are enough, because all other are based on them. |
|
#4462 looks interesting btw. |
|
Based on them, but as I see that you are already aware, only actually including them at some point in the (potentially far) future. |
No description provided.